Method of and a network server and mobile user equipment for providing chat/VoIP services in a mobile telecommunications network

ABSTRACT

A method of and an application server and user equipment for providing at least one of chat and Voice over Internet Protocol, chat/VoIP, services to the mobile user equipment in a mobile telecommunications network. The mobile user equipment comprises a chat/VoIP client for accessing a chat/VoIP service application interfacing the mobile telecommunications network. The chat/VoIP service application interfaces a plurality of proprietary chat/VoIP clients for accessing a plurality of proprietary chat/VoIP communication environments operated by a plurality of chat/VoIP service providers, for providing chat/VoIP services to the chat/VoIP client of the mobile user equipment. The chat/VoIP client and the chat/VoIP service application may be arranged such that privileged use of the mobile telecommunications network is enabled, providing a session between the user equipment and a communication environment with a predetermined or agreed Quality of Service.

RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 15/923,321, which was filed Mar. 16, 2018, which is acontinuation of U.S. patent application Ser. No. 15/652,952, which wasfiled Jul. 18, 2017, now U.S. Pat. No. 9,930,564, which is acontinuation of U.S. patent application Ser. No. 14/918,726, which wasfiled on Oct. 21, 2015, now U.S. Pat. No. 9,723,512, which is acontinuation of U.S. patent application Ser. No. 13/140,270, which wasfiled on Jul. 15, 2011, now U.S. Pat. No. 9,203,873, which is a nationalstage application of PCT/EP2008/010777, filed Dec. 17, 2008, thedisclosures of each of which are incorporated herein by reference intheir entirety.

TECHNICAL FIELD

The present invention relates to handling of services in a mobilecommunications network, in particular chat and Voice over InternetProtocol, VoIP, services in plurality of dedicated or proprietary chatand VoIP communication environments.

BACKGROUND

Several providers of voice services over Internet Protocol, IP, offerchat and VoIP services, called chat/VoIP, in a dedicated or proprietarychat and VoIP communication environment. A user can register in such aproprietary chat/VoIP communication environment with an appropriateunique identity, ID, or “nickname”. When registered, the user has todownload and install client software on his User Equipment, UE, whichsoftware is required and used to communicate with other registeredusers, called “buddies”, within that particular chat/VoIP communicationenvironment. Often communication, chat and/or VoIP, within suchchat/VoIP communication environment is free-of-charge, whereascommunication with users in other communication environments operated bydifferent chat/VoIP providers and providing similar chat/VoIP servicesor public telephony services can be more difficult, not free-of-charge,or not possible at all.

Chat/VoIP clients are designed for Personal Computers, PCs, which have awired connection (often broadband) to the internet and for wireless ormobile UE, such as but not limited to portable computers or laptops,Personal Digital Assistant, PDA, terminals and mobile phones.

To communicate in different chat/VoIP communication environmentsoperated by different chat/VoIP providers, the user may registerseparately in all these communication environments, to get a unique IDor nickname and appropriate client software and has to download andinstall additional proprietary client software on his UE.

When using chat/VoIP services (pre)installed or embedded at a mobile UEoperating in a Radio Access Network, RAN, under control of a mobilenetwork provider, the UE and the RAN select a data packet channel thatprovides a required Quality of Service, QoS, for conducting a voicecall, for example. This, because the chat/VoIP client installed on theUE, called the UE chat/VoIP client, is an integral part of the UE, i.e.operating under the communication protocol supported by the UE and theRAN and has received sufficient “privileges” to support the requiredpredefined QoS, i.e. operates in a privileged mode. The RAN may be amobile network arranged for supporting Global System for Mobilecommunications, GSM, a General Packet Radio Service, GPRS, or aUniversal Mobile Telecommunications System, UMTS, for example. Themobile network provider maintains subscriptions of UEs for users of theRAN for accessing chat/VoIP communication services with an agreed orpredefined QoS.

A chat/VoIP provider that provides chat/VoIP services in a chat/VoIPcommunication environment under control of the mobile network providerin a RAN with a privileged mode, either a proprietary or a standardizedchat/VoIP client, is regarded as a privileged chat/VoIP provider,whereas other chat/VoIP providers cannot use the RAN with the sameprivileged mode.

When a chat/VoIP provider provides a proprietary UE chat/VoIP clientthat can be installed as an application on the UE, in addition to the(pre)installed or embedded UE chat/VoIP client, this proprietary UEchat/VOIP client however does not have special rights or privileges.This UE chat/VoIP client software runs in a “non-privileged” mode andgets IP-connectivity with only “best effort” quality, as thecommunication link over the RAN will not be selected on the basis of adefined QoS. It depends on the arrangement and availability of the RANwhether the “best effort” quality is enough for VoIP. When UMTS isavailable, for example, VoIP should be possible. Otherwise thetransmission may not be suitable for VoIP. The user may notice adifference in quality of chat/VoIP communication sessions when using achat/VoIP connection operated via a RAN with a guaranteed QoS comparedto a chat/VoIP connection when using a RAN with only “best effort”quality.

A possible solution to this problem might be to have the UE vendor andthe chat/VoIP provider agree that an additionally installed UE chat/VoIPclient on the UE may also use like functions and privileges as providedto the already (pre)installed or embedded UE chat/VoIP client, such asselecting “privileged” communication facilities of the RAN providing arequired QoS.

However, this solution requires that the UE chat/VoIP client software istrusted SoftWare, SW, for installing on the UE and operating with theRAN. Security-minded users might hesitate to install and deploy suchproprietary UE chat/VoIP client software of chat/VoIP providers on theirUE.

Moreover most or probably not all chat/VoIP providers will have theirproprietary UE chat/VoIP client ported to all types of mobile phones.Such that not all proprietary chat/VoIP communication environments canbe accessed by all mobile users, which hampers universal and effectiveuse of the chat/VoIP services.

SUMMARY

It is an object of the present invention to provide an efficient, userfriendly, trusted and efficient solution for communicating with mobileUE in different, proprietary or standardized chat/VoIP communicationenvironments operated by different chat/VoIP providers, as well as anetwork node or application server for a mobile communications networkand mobile UE equipped for supporting such method.

A first aspect comprises a method of providing at least one of chat andVoice over Internet Protocol, chat/VoIP, services to a mobile UE in amobile telecommunications network, the mobile UE comprises a UEchat/VoIP client for accessing a chat/VoIP communication environment.There is provided a chat/VoIP service application interfacing the mobiletelecommunications network and interfacing a plurality of applicationserver chat/VoIP clients for accessing a plurality of chat/VoIPcommunication environments operated by a plurality of chat/VoIP serviceproviders, for providing chat/VoIP services to the UE chat/VoIP clientby each accessed chat/VoIP communication environment.

Different from the prior art solutions, wherein a chat/VoIPcommunication environment is directly accessed under the control of anappropriate, i.e. proprietary or standardized, UE chat/VoIP clientinstalled on the UE, with the invention the chat/VoIP serviceapplication and the respective application server chat/VoIP clients actas an interface for the UE chat/VoIP client for accessing a plurality ofchat/VoIP communication environments.

Accordingly, a single UE chat/VoIP client on a UE is sufficient foraccessing different chat/VoIP communication environments, therebyeffectively preventing downloading and installing of differentproprietary or standardized chat/VoIP UE clients on the UE, andpreventing the accompanying disadvantages such as waste of costly memoryand processor capacity on the UE. In particular when a relatively largenumber of different chat/VoIP communication environments have to beaccessed. Also the need for the development of a plurality of differentUE chat/VoIP clients for different types of UE and different types ofchat/VoIP communication environments and is effectively avoided.

In an example of the invention, interfacing by the chat/VoIP serviceapplication comprises:

-   -   connecting to the UE chat/VoIP client,    -   connecting to at least one of the plurality of application        server chat/VoIP clients,    -   acting as a chat/VoIP client towards a connected chat/VoIP        communication environment, the chat/VoIP communication        environment being proprietary or standardized, and    -   acting as a chat/VoIP communication environment towards the UE        chat/VoIP client.

To effectively solve problems caused by lack of coordination betweenseveral chat/VoIP communication environments, in a further example ofthe invention the application server chat/VoIP clients provide protocolconversion between a proprietary or standardized chat/VoIP communicationenvironment and the chat/VoIP communication environment provided by thechat/VoIP service application acting towards the UE chat/VoIP client.

It will be appreciated that the protocol conversion may effectivelysolve and prevent interference problems caused by the simultaneousexecution of several chat/VoIP clients.

Users of chat/VoIP services are used to the concept of “nicknames” thatis that each user in a chat/VoIP communication environment has a uniquenickname or identification under which the user can be addressed in thecommunication environment. The nickname is usually an ASCII-string.

The concept of nicknames can be effectively supported and adhered to inthe present invention, in a further example of which wherein thechat/VoIP service application interfaces the UE chat/VoIP client and theplurality of application server chat/VoIP clients for accessingfunctions of a chat/VoIP communication environment, among whichproviding status information of a UE, updating status of buddies,setting up sessions, and accepting sessions.

In a very user friendly example, the chat/VoIP service applicationprovides a single private address book accessible for the UE chat/VoIPclient for defining and storing a local nickname or identity inassociation with a unique nickname or identity created by the chat/VoIPservice application for each buddy in a respective proprietary orstandardized chat/VoIP communication environment. The chat/VoIP serviceapplication determines which unique nickname or identity to be used fora specific chat/VoIP communication environment.

The user may select own local nicknames, which can be more easily toremember as the nicknames provided by the chat/VoIP service application.When the user communicates with the system, only the local nicknameshave to be used. The chat/VoIP service application determines whichchat/VoIP communication environment to use with a selected nickname.

In a second aspect, there is provided an application server for use in amobile telecommunications network, comprising processing equipment andcommunication equipment. The processing equipment is arranged forproviding, via the communication equipment, at least one of chat andVoice over Internet Protocol, chat/VoIP, application services to a UEchat/VoIP client in the mobile telecommunications network. The chat/VoIPapplication service processing equipment is arranged for interfacing aplurality of proprietary or standardized application server chat/VoIPclients for accessing, via the communication equipment, a plurality ofproprietary or standardized chat/VoIP communication environmentsoperated by a plurality of chat/VoIP service providers for providing,via the communication equipment, chat/VoIP services to the UE chat/VoIPclient by each accessed chat/VoIP communication environment.

In a particular example, the chat/VoIP service application processingequipment and the communications equipment are arranged for supportingSession Initiation Protocol, SIP, signalling in an IP MultimediaSubsystem, IMS.

For supporting an address book of nicknames, in an example, theapplication server comprises storage equipment interfacing the chat/VoIPservice application processing equipment, which storage equipment isaccessible, via the communication equipment, to a UE chat/VoIP client ofmobile UE for defining and storing a local nickname or identity inassociation with a unique nickname or identity for use in at least oneof the chat/VoIP communication environments.

In a further example, the processing equipment of the application serveris arranged for communication, via the communication equipment, with aUE chat/VoIP client of mobile UE, in a manner such that privileged useof the mobile telecommunications network is provided.

By having the interfacing functions with the UE chat/VoIP client and thechat/VoIP communication environments provided by or under control of theapplication server, which can be operated under control of or inaccordance with a negotiated agreement with a mobile network provider,for accessing each proprietary or standardized chat/VoIP communicationenvironment, the communication over the mobile telecommunicationsnetwork is supported under the rights and privileges granted by themobile telecommunications network and, accordingly, allows use ofspecial rights and privileges assigned, such as QoS for a particularservice, like speech. Accordingly, privileged communication by thechat/VoIP communication environments other than that provided by themobile telecommunications network provider is enabled. Because theapplication server can operate under an agreement with the mobiletelecommunications network provider, there is no separate agreementrequired with each UE/OS vendor on a proprietary interface, for eachtype of UE. Further, no security key exchange of a user with aproprietary chat/VoIP provider is required in case of installedchat/VoIP SW, with privileged use, requiring a security key.

A third aspect comprises a method of providing at least one of chat andVoice over Internet Protocol, chat/VoIP, services by processingequipment in an application server of a mobile telecommunicationsnetwork, the method comprises the steps of:

-   -   acting as a chat/VoIP client towards a chat/VoIP communication        environment, the chat/VoIP communication environment being        proprietary or standardized,    -   acting as a chat/VoIP communication environment towards a        chat/VoIP client of UE in the mobile telecommunications network,        and    -   protocol conversion between a proprietary or standardized        chat/VoIP communication environment and the chat/VoIP        communication environment provided towards the UE chat/VoIP        client.

The application server is a node connected to the internet orincorporated in a network server or network node of thetelecommunications network.

In an example, the protocol conversion comprises coordinating andmapping of chat/VoIP services, features and functions of a chat/VoIPcommunication environment to and from a UE chat/VoIP client. Examples ofsuch services, features and functions is reporting a status change ofthe UE chat/VoIP client to the at least one proprietary or standardizedchat/VoIP communication environment, a status change of a buddy in theat least one proprietary chat/VoIP communication environment to the UEchat/VoIP client, and others.

In another example, the steps of acting as a chat/VoIP client and actingas a chat/VoIP communication environment in the application servers,comprise setting up and accepting chat/VoIP communication sessionsproviding privileged use of the mobile telecommunications network, inparticular providing an agreed Quality of Service, QoS.

In case a chat/VoIP client SW is allowed to install its proprietary orstandardized chat/VoIP interface on the application server, resulting ina privileged RAN use, the chat/VoIP provider is NOT required to updatehis or her chat/VoIP interface each time the Operating System vendorupdates same, or that the UE vendor adds or changes functionality in theUE, which seems to be a frequently occurring event due to marketevolution.

In a fourth aspect, there is provided mobile User Equipment, UE,comprising processing equipment connected to input and output equipmentand communication equipment, wherein the processing equipment isarranged for providing, via the input and output equipment andcommunication equipment, at least one of chat and Voice over InternetProtocol, chat/VoIP, services, by processing a UE chat/VoIP client. TheUE chat/VoIP client processing equipment is arranged for processing theUE chat/VoIP client for accessing chat/VoIP services of a plurality ofproprietary or standardized chat/VoIP communication environments via anapplication server, wherein the UE chat/VoIP client is arranged toGraphical User differences of the plurality of chat/VoIP communicationenvironments.

In a further example of the mobile UE, the UE chat/VoIP client isarranged to provide a single Graphical User Interface, GUI, via inputand output equipment for the plurality of chat/VoIP communicationenvironments. A single GUI is advantageous for the user, which does notneed to learn and know proprietary interfaces as many as differentchat/VoIP communication environments in which the user would like tohave sessions.

In another example, it is advantageous in that the mobile UE comprises alocal database connected to the processing equipment for storing andretrieving records comprising nicknames corresponding to nicknames usedin the chat/VoIP communication environments.

The invention is particularly suitable with a mobile telecommunicationsnetwork or platform for supporting rich multimedia communications suchas an IP Multimedia Subsystem, IMS, wherein the chat/VoIP serviceapplication supports Session Initiation Protocol, SIP, signalling andthe UE chat/VoIP client operates as an IMS-based chat/VoIP client.

Accordingly, in a further example, the UE chat/VoIP processing equipmentand communication equipment supports IP Multimedia Subsystem, IMS SIPsignalling.

The above-mentioned and other features and advantages of the inventionwill be best understood from the following description referring to theattached drawings. In the drawings, like reference numerals denoteidentical parts or parts performing an identical or comparable functionor operation.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows, in a schematic and illustrative manner, a prior artsolution of chat/VoIP communication service with a plurality ofproprietary or standardized chat/VoIP communication environments from asingle user equipment.

FIG. 2 shows, in a schematic and illustrative manner, chat/VoIPcommunication from a single user equipment with a plurality ofproprietary or standardized chat/VoIP communication environments inaccordance with an example of the invention.

FIG. 3 illustrates a method performed by an application server arrangedfor providing chat/VoIP services to mobile UE in accordance with anexample of the invention.

FIG. 4 illustrates signalling steps when a user of an IMS-based UEchat/VoIP client registers to a chat/VoIP communication environment inaccordance with an example of the invention.

FIG. 5 illustrates signalling steps when a user of the IMS-based UEchat/VoIP client starts chat/VoIP communication sessions.

DETAILED DESCRIPTION

The present invention will now be illustrated by way of example and notby way of limitation in a Radio Access Network, RAN, for mobilecommunication such as a Global System for Mobile communications, GSM, aGeneral Packet Radio Service, GPRS, or a Universal MobileTelecommunications System, UMTS, network supporting communication withmobile User Equipment, UE, operating in or from a RAN, for the handlingof media types such as video, including streaming video, images, audio,Voice over Internet Protocol, VoIP, chat services and data sharing on adata packet oriented communication basis. Hereinafter designatedchat/VoIP services. The RAN is operated by or under the control of amobile network provider.

In FIG. 1, reference numeral 1 indicates a prior art UE such as, but notlimited to, a mobile telephone, mobile laptop computer, Personal DigitalAssistant, PDA, etc. The UE 1 comprises a processor 3 connected to anInput/-Output, I/O, subunit 2, comprising input devices 2 a such as akeyboard, mouse, microphone, etc. and output devices 2 c such as adisplay, loudspeaker, etc. The I/O subunit 2 further comprises acommunication transceiver 2 b for exchanging data with a mobiletelecommunications network, i.e. RAN 30.

Reference numeral 20 indicates the Internet, to which several devices24, 25, 26 that host chat/VoIP communication environments connect, i.e.a chat/VoIP communication environment A, 21; a chat/VoIP communicationenvironment B, 22; and a chat/VoIP communication environment C, 23,respectively. All these chat/VoIP communication environments 21, 22, 23are either standardized or proprietary, i.e. non-standardized, andhosted or operated by different chat/VoIP service providers. Althoughjust three chat/VoIP communication environments have been shown, inpractice more or less chat/VoIP communication environments are feasible,and chat/VoIP communication environments operating in other networks,public or private. All this is to be considered as being encompassed bythe environments and network shown.

For communication with each chat/VoIP communication environment 21, 22,23 appropriate communication, control and user interfacing software,called UE chat/VoIP clients, are installed on the UE 1, i.e. UEchat/VoIP client A, 11, for providing chat/VoIP services with chat/VoIPcommunication environment A, 21; UE chat/VoIP client B, 12, forproviding chat/VoIP services with chat/VoIP communication environment B,22; and UE chat/VoIP client C, 13, for providing chat/VoIP services withchat/VoIP communication environment C, 23. Each UE chat/VoIP client 11,12, 13 applies an application protocol for Internet Protocol, IP, peerto peer connectivity to the chat/VoIP communication environment 21, 22,23, schematically indicated by dashed arrows 31, 32, 33, respectively.The UE chat/VoIP clients 11, 12, 13 on the UE 1 are executed undercontrol of an Operating System, OS 3 a, processed by the processor 3.

The chat/VoIP communication environments 21, 22, 23 are processesrequired for establishing and maintaining specific chat/VoIPcommunication sessions. These processes are executed at devices 24, 25,26 such as servers and/or terminals connected to the Internet 20.Examples of such devices 24, 25, 26 are:

-   -   a terminal, such as a UE, that hosts a Chat/VoIP communication        environment 21, 22, 23, and supports, for example, a        communication session, such as a voice call, with a UE chat/VoIP        client 11, 12, 13 executed at UE 1;    -   a server that hosts a chat/VoIP communication environment 21,        22, 23 and used, for example, to monitor the status of a UE        chat/VoIP client 11, 12, 13 executed at UE 1, or to control a        registration request of a UE chat/VoIP client 11, 12, 13, or to        control a communication session between a UE chat/VoIP client        11, 12, 13 and a chat/VoIP client executed at, for example,        another terminal.

For identifying purposes, in the chat/VoIP communication environments21, 22, 23 users are known and registered under “nicknames”. Thesenicknames are stored in an address book at the UE 1, one for each UEchat/VoIP client 11, 12, 13, schematically indicated by databases 14,15, 16. In an address book nicknames may be stored of other users of thecorresponding chat/VoIP environment, called “buddies”. It will beappreciated that this information may also be stored in a databaseprovided by a chat/VoIP provider (not shown). Further, statusinformation may be stored in the address book, i.e. permanent ortemporary information, for example availability of a buddy or other datarelating to a chat/VoIP communication.

UE chat/VoIP clients 11, 12, 13 are applications that are enabled by anApplication Program Interface, API, and executed by the processor 3under control of the OS 3 a. The UE chat/VoIP client applications 11,12, 13 are respectively executed via API 11 a, 12 a and 13 a. The APIcan be distinguished in an either proprietary or standardized interface.If proprietary, the API is meant to be used by a single chat/VoIPprovider, not allowing other chat/VoIP providers to use this API. Astandardized API applies published interfaces to the OS 3 a, such thatchat/VoIP providers are enabled to design chat/VoIP applicationsenabling execution of functions by means of processor 3 under control ofOS 3 a.

The API may further be distinguished in a privileged and non-privilegedinterface, where privileges may comprise:

-   -   enabling a download of an application, where this download only        succeeds when the application comprises some form of a security        key;    -   installing or executing a downloaded application which is        allowed under a specific condition, such as complying with a        security check;    -   executing certain functions by the processor 3 in a specific        way, e.g. the setup of a network path via the RAN is according        to a specific Quality of Service, QoS.

In practice, OS 3 a may support several APIs, where these APIs arecharacterized by combinations of proprietary/standardized andprivileged/non-privileged interfaces.

For the purpose of explanation, it is now assumed that UE chat/VoIPclient 11 is (pre)installed on the UE 1 by the radio network provider ofthe RAN 30, such that this UE chat/VoIP client 11 applies a proprietaryand privileged API 11 a. Optionally this UE chat/VoIP client 11 may beembedded within the OS of UE 1 together with API 11 a.

For the purpose of explanation it is further assumed that the UEchat/VoIP clients 12, 13 are not (pre)installed by the network providerof the RAN 30, but additionally initialised by the user, for examplewhen registering for the first time at the corresponding chat/VoIPcommunication environment 22, 23. The UE chat/VoIP client 12 is aproprietary client different from client 11 and applies thenon-privileged API 12 a. The UE chat/VoIP client 13 is a standardizedclient different from clients 11 and 12 and applies the non-privilegedAPI 13 a.

Because the UE chat/VoIP client 11 applies the privileges enabled by API11 a, its peer to peer communication session 31 is set up using allprivileges and rights provided and/or predefined by the OS 3 asupporting API 11 a, such as a privileged use of RAN 30 with acommunication protocol according to a required QoS, for VoIP. The IPconnectivity for the communication session 31 is arranged viatransceiver 2 b, RAN 30, and Internet 20, towards an IP interface ofdevice 24.

The use of RAN 30 is in this case a so called “privileged” use asnetwork parameters for the agreed QoS, such as a guaranteed bandwidth,latency and iso-synchronity are applicable. This can be the case where,for example, the user of UE 1 has a subscription with the RAN provider,obliging the RAN provider to deliver an agreed QoS for communicationsession 31.

To the contrary, the chat/VoIP communication sessions 32, 33 initiatedby the proprietary chat/VoIP UE clients 12, 13 cannot benefit from the“privileged” use of RAN 30 as non-privileged APIs 12 a, 13 a do notsupport special rights or privileges. The execution of non-privileged UEchat/VoIP client applications 12, 13 results in a non-privileged use ofRAN 30 based on “best effort”. Not receiving a guaranteed QoS for achat/VoIP communication session may result in poor speech communication,for example, or no speech communication at all.

Using the privileged API 11 a by the chat/VoIP provider of UE chat/VoIPclient 12, 13 is not an option, as the OS 3 a does not allow to use API11 a, being a proprietary API installed or provided by the RAN provider,by any other UE chat/VoIP client than client 11.

FIG. 2 shows an example of the invention. UE 40 comprises an InternetProtocol, IP, based User Equipment, UE, chat/VoIP client 41, whichenables a privileged use of the RAN 30, for all chat/VoIP communicationenvironments used by a user of UE 40 as disclosed above in connectionwith FIG. 1.

As to solve the problem of having only “best effort” IP connectivity forchat/VoIP communication sessions 32, 33, provided by chat/VoIP providersthat cannot use a privileged API, the UE 40 applies a single UEchat/VoIP client 41.

This UE chat/VoIP client 41 will be provided by a UE vendor, a RANnetwork provider or a chat/VoIP provider who has arrangements with theRAN network provider for providing privileged use of the RAN 30.

UE chat/VoIP client 41 interfaces to the OS 3 a via API 41 a, which isdesigned to provide a “privileged” use of RAN 30 for achieving an agreedQoS. Processor 3, under control of OS 3 a of the UE 40, is arranged, asin FIG. 1, to initiate IP connectivity to the internet 20 via thetransceiver 2 b and RAN 30, when UE chat/VoIP client 41 operates as asingle chat/VoIP client for communication sessions with multiplechat/VoIP environments 21, 22, 23.

The RAN 30 and the Internet 20 comprise processing and communicationmeans for executing a call setup request from the UE chat/VoIP client 41to a chat/VoIP service application 54 at an Application Server, AS, 50via RAN 30 and Internet 20, in accordance with the invention.

With reference to FIG. 2, the AS 50 has a processor 55, under control ofan Operating System (OS) 56 and is connected to an I/O subunit 57 forexchange of data. The AS 50 is connected and communicates by means ofthe I/O subunit 57 via the Internet 20 or a proprietary link to the RAN30 (shown in dashed lines).

AS 50 can be a node connected to the internet 20 or can be incorporatedin an application or network server or network node of thetelecommunications network, i.e. the RAN 30. It is proposed that the AS50 operates under control of the provider of the RAN 30 or at least atrusted party with respect to the user of UE 40.

The part of the Internet 20 shared by the RAN 30 and the AS 50 can bedeployed alternatively to the Internet 20 as, for example, a separateconnection, a Circuit Switched network or Asynchronous Transfer Modenetwork connected via secure means, such as a firewall, to the globalInternet 20 for security reasons or bandwidth requirements. Optionallythis part of the Internet 20 is configured as a separate environment 20a for security reasons.

The AS 50 executes a universal chat/VoIP service application 54, whichis arranged to perform client and server tasks for a plurality ofproprietary or standardized AS chat/VoIP clients 51, 52, 53 arranged forcommunication to a plurality of the chat/VoIP communication environments21, 22, 23, respectively. AS chat/VoIP clients 51, 52, 53 constitutesoftware or hardware that is designed to cooperate with the universalchat/VoIP service application 54. The AS chat/VoIP client 51, 52, 53provides a protocol conversion between a proprietary or standardizedchat/VoIP communication environment 21, 22, 23 and the serviceapplication 54.

The universal chat/VoIP service application 54 is arranged to perform acoordinating and mapping of specific chat/VoIP services environmentfeatures or functions, such as icon-function and -representation, to andfrom the single user interface represented at UE 40 by means of UEchat/VoIP client 41. Providers of Chat/VoIP services have to agree withthe provider of the RAN 30 on a set of capabilities of RAN 30 to beused, such as the privileged use, and provide the AS chat/VoIP clientsoftware 51, 52, 53 that cooperates with service application 54, as tobenefit from the universal use of the invention.

The provider controlling the AS 50 provides a suitable interface or APIto the service application 54, that according to the agreement with thechat/VoIP provider supports a QoS that allows to define a minimumbandwidth of the RAN, designated as “privileged” RAN use, instead ofrelying to the RAN's “best effort” basis.

Apart from a privileged RAN use, other features, such as use of networkservices, can be agreed between the provider of the AS 50 and thechat/VoIP provider, enabled by means of service application 54.

Service application 54 is further arranged to communicate, in aproprietary or standardized way, with UE chat/VoIP client 41 via API 41a at UE 40, such that the privileged use of the RAN 30 is guaranteed.

As an example, if a buddy status of chat/VoIP environment A 21 changes,AS chat/VoIP client 51 signals this status change to service application54, and subsequently service application 54 decides to signal UEchat/VoIP client 41, which may represent this status change at the userinterface of UE 40.

Further examples of functions of the universal chat/VoIP serviceapplication 54 are setting up chat/VoIP communication sessions andaccepting chat/VoIP communication sessions.

Other functions that the service application 54 may perform are, but notlimited to:

-   -   acting as interworking unit for signalling between an AS        chat/VoIP client 51, 52, 53 and the chat/VoIP client 41;    -   coordinating input and/or output streams between an AS chat/VoIP        client 51, 52, 53 and the chat/VoIP client 41;    -   providing access to services offered by the mobile        telecommunications network RAN 30 for an AS chat/VoIP client 51,        52, 53;    -   reading and representing at the UE 40 in a single Graphical User        Interface, GUI, statuses from different AS chat/VoIP clients 51,        52, 53;    -   selecting which AS chat/VoIP client 51, 52, 53, to use when        setting up a chat/VoIP session from UE 40.

Service application 54 can be implemented as a sub-unit within AS 50 aseither hardware or software.

UE chat/VoIP client 41 is arranged to perform a general chat/VoIP userinterface in cooperation with service application 54 to the user of UE40, using input devices 2 a and output devices 2 c. API 41 a is providedby the OS vendor (or UE vendor when the OS 3 a is comprised by the UE40) and is designed to support UE chat/VoIP client 41 with privilegedRAN 30 use.

As indicated above, although just three chat/VoIP communicationenvironments have been shown, in practice more or less chat/VoIPcommunication environments are feasible and chat/VoIP communicationenvironments operating in other networks, public or private. All this isto be considered as being encompassed by the environments and networkshown.

Referring back to FIG. 1 and, as illustratively shown in FIG. 2, thechat/VoIP communication sessions 31, 32, 33 although operating ondifferent chat/VoIP communications environments 21, 22, 23 now, in theexample of the invention, receive privileged RAN QoS treatment, via API41 a by means of processor 3 under control of OS 3 a of the UE 40, whilethe UE chat/VoIP client 41 operates as the universal chat/VoIP clientfor communication sessions 31, 32, 33.

UE chat/VoIP client 41, in cooperation with service application 54 andthe AS chat/VoIP client 51, 52, 53 is regarded as a universal chat/VoIPclient service. Chat/VoIP communication environment 21, 22, 23 willnotice no difference between a session towards UE chat/VoIP client 11,12, 13 with respect to FIG. 1, and a session towards AS chat/VoIP client51, 52, 53 with respect to FIG. 2.

While effectively avoiding the need for downloading, installing, andexecuting of different, proprietary, software UE chat/VoIP clients 11,12, 13 on the UE, in this example of the invention, the user of the UE40 maintains the possibility of communication with all the chat/VoIPcommunication environments 21, 22, 23 registered with, and has thebenefit of applying chat/VoIP communication sessions via a privilegedRAN connection according to an agreed QoS for each chat/VoIP provider.

The AS chat/VoIP client 51, 52, 53 executed at the AS 50 can beappropriately developed and maintained by a mobile RAN 30 networkprovider in connection with chat/VoIP service providers.

In FIG. 2, the IP peer to peer connectivity between the UE 40 and thechat/VoIP environments 21, 22, 23, executed at devices 24, 25 and 26respectively are depicted as dashed lines 71, 72, 73. According to theinvention, there is not a one to one IP peer to peer connection withcommunication sessions 31, 32 and 33, as shown in FIG. 1, but a steppedconnection comprising:

-   -   a single IP peer to peer link 70 between the UE 40 comprising UE        chat/VoIP client 41 and the service application 54 comprised by        AS 50;    -   a one to many IP peer to peer link 71, 72, 73, from the AS 50        comprising service application 54, to the devices 24, 25, 26        comprising the chat/VoIP communication environments 21, 22, 23.

FIG. 3 illustratively shows an example of steps performed by the AS 50,i.e. the service application 54 an the AS chat/VoIP client 51, 52, 53for providing chat/VoIP services between UE 40 and communicationenvironment A, 21, for example.

It is assumed that UE chat/VoIP client 41 initiates a chat/VoIP sessionand connects to processing equipment 54, 55, 56 of the AS 50, via thetransceiver 2 b of the UE 40, RAN 30 and the I/O subunit 57 of the AS50. In response to this connection, the AS 50 acts as a chat/VoIPenvironment towards the UE chat/VoIP client 41.

Based on the information provided by the UE chat/VoIP client 41, such asthe nickname of a user to be contacted in the chat/VoIP communicationenvironment A, 21, the processing equipment 54, 55, 56 of the AS 50contacts the chat/VoIP communication environment A, 21, via theappropriate AS chat/VoIP client 51, and acts a chat/VoIP client towardsthe communication environment A, 21. Although shown separately, it willbe appreciated that the AS chat/VoIP client 51 may be integral to theprocessing equipment 54, 55, 56 of the AS 50.

In the chat/VoIP session established, the AS 50 provides protocolconversion for the communication and services exchanged between thechat/VoIP communication environment A, 21, and the UE chat/VoIP client41 of the UE 40.

In the event that the communication environment A, 21, initiates achat/VoIP session towards the UE 40, the AS 50 likewise acts a chat/VoIPclient towards the communication environment A, 21 and as a chat/VoIPcommunication environment towards the UE chat/VoIP client 41.

For further chat/VoIP session between the UE 40 and other chat/VoIPcommunication environments B, 22, or C, 23, the AS 50 acts as aproprietary or standardized chat/VoIP client 52, 53 for the chat/VoIPcommunication environments B, 22, or C, 23, respectively, but as auniversal chat/VoIP communication towards the UE chat/VoIP client 41 ofthe UE 40.

Without being restricted to any to any technology for implementation,the invention is further elucidated by means of an implementation in anInternet protocol Multimedia Subsystem, IMS, core network 60.

The IMS-core network 60 enables rich multimedia communications sessionswith the UE 40 for the handling of chat/VoIP services, but also handlingof media types such as video, including streaming video, images, audio,and data sharing on a data packet oriented communication basis. For theremainder of this description, the term chat/VoIP represents all themedia types listed above where appropriate. IMS unifies applicationsthat are based on Session Initiation Protocol, SIP, signalling whichenables multimedia sessions.

The UE 40 comprises a single, IMS based, UE chat/VoIP client 41. This UEchat/VoIP client 41 will be provided by a provider who has arrangementswith the RAN 30 network provider who can also provide the IMS-corenetwork 60, or has an agreement with an IMS-core network 60 networkprovider.

The IMS-core network 60 operates by means of a plurality of servers, ornodes, such as a Serving Call Session Control Function, S-CSCF, anInterrogating Call Session Control Function, I-CSCF, and a Proxy CallSession Control Function, P-CSCF, designated by reference numeral 61.The S-, I- and P-CSCF servers 61 comprise processing and communicationmeans for executing a call setup request initiated by the UE chat/VoIPclient 41 to a chat/VoIP service application 54 at the AS 50 inaccordance with the invention, supporting a Session Initiation Protocol,SIP, signalling, hereinafter called SIP-AS, 50.

As additional to illustrated above, the part of the Internet 20 sharedby the RAN 30, the SIP-AS 50 and the IMS-core network 60, a part 20 a,can optionally be configured as a separate environment for securityreasons.

With reference to the FIGS. 4 and 5 examples of signalling scenarios forchat/VoIP communication sessions in accordance with the invention willbe discussed.

For the ease of explanation, the setup of a connection by the UE 40towards the SIP-AS 50 by means IMS-core network 60 is regarded asaccomplished according to prior art methods. Receiving or sendingsignals at SIP-AS 50 is performed by I/O subunit 57 connected to theprocessor 55 under control of OS 56.

Referring to FIG. 2, before any communication with the chat/VoIPenvironment 21, 22, 23 is able, the user of UE 40 has to register to theenvironment 21, 22, 23. This registration action is has to be done onceand may be performed by a device capable to connect to the environment21, 22, 23, such as UE 40, but also from various other devices, such asa Personal Computer. The user of UE 40 can use different or identicalnicknames in each environment 21, 22, 23.

The registration action initialized at UE 40 is performed by selecting amenu option at the UE 40, provided by UE chat/VoIP client 41, listingthe available environments 21, 22, 23, corresponding to the available ASchat/VoIP clients 51, 52. 53 present at SIP-AS 50.

For each environment 21, 22, 23 registered to, the user may select itsown nickname, which is stored in a database 58 as a record, “ownnickname—environment name” for the user of UE 40. Database 58 iscommunicatively connected to service application 54. A required passwordfor each environment 21, 22, 23 might either be stored at database 58,stored at UE 40 in database 6 or provided on request by the user of UE40. The database 6 is communicatively connected to UE chat/VoIP client41. FIG. 4 shows registration in chat/VoIP communication A and B 21, 22,with nicknames A, B, respectively.

Referring to FIG. 4 when a user starts his IMS-based UE chat/VoIP client41 on his UE 40, the service application 54 of SIP-AS 50 is notified ofthis action, using the SIP REGISTER message, as usual for the IMSPresence service. Alternatively the start-up of UE chat/VoIP client 41is initialized by powering on the UE 40.

On starting up UE chat/VoIP client 41, this client 41 signals theservice application 54 on its status change. Service application 54retrieves the records “own nickname—environment name” record for theuser of UE 40 from its database 58 and informs the appropriateenvironments, by signalling the appropriate available AS chat/VoIPclient 51, 52, 53 that acts towards the chat/VoIP communicationenvironment 21, 22, 23 as normal client-SoftWare (client-SW) that hasbeen started.

These “client-SW” AS chat/VoIP clients 51, 52, 53 report themselves(FIG. 4 “start client”) to the chat/VoIP environments 21, 22, 23 withtheir appropriate nickname and status of the user of UE 40, and receivefrom the environments 21, 22, 23 status information (FIG. 4 “status msg. . . ”) as belonging to the users in the buddy-lists within theseenvironments 21, 22, 23. The service application 54 of SIP-AS 50combines the received status information from the different environments21, 22, 23 into status information as according to IMS Presence. Anyrequired password may be provided as suggested above.

When the user of the UE 40 changes his status e.g. to unavailable forall chat/VoIP communication sessions, the UE chat/VoIP client 41 reportsthis change to the service application 54 of SIP-AS 50, the serviceapplication 54 reports this status change to all involved chat/VoIPcommunication environments 21, 22, 23 via AS chat/VoIP clients 51, 52,53 for the appropriate chat/VoIP environments where the user of UE 40has been registered, i.e. where the database 58 comprises environmentrecords “nickname—environment” for, and which are available.

In case a buddy of a chat/VoIP environment 21, 22, 23 changes itsstatus, the involved chat/VoIP environment 21, 22, 23 reports thischange to the service application 54 at SIP-AS 50 via the AS chat/VoIPclient 51, 52, 53, and the service application 54 reports this change inturn to the UE chat/VoIP client 41, which can display this informationto the user at the display 2 c.

When the user of UE 40 sets up an outgoing chat/VoIP communicationsession with as “called party” a buddy of the chat/VoIP environment 21,22, 23, an IMS session is started towards service application 54 bysending a SIP INVITE message to SIP-AS 50. As an example a chat/VoIPsession to buddy “Bob128” from the buddy list is started up by the userof UE 40, wherein “Bob128” is a nickname for a buddy or party fromenvironment B, stored in database 58.

The service application 54 of SIP-AS 50 handles this setup by checkingin database 58 to which chat/VoIP communication environment A, B or C21, 22, 23 the “called party” belongs. The service application 54selects the appropriate AS chat/VoIP client 51, 52, 53 to set up acommunication session within that communication environment 21, 22, 23.

In case “Bob128” is defined in more than one chat/VoIP environment 21,22, 23, a message is sent by service application 54 to the UE 40offering the user a menu listing the environments to select from. Whenthe “called party” accepts, a chat/VoIP-session is started.

In the case of an incoming request for a chat/VoIP session, a buddywithin the chat/VoIP communication environment 21, 22, 23 e.g. “Bob128”in chat/VoIP-environment B 22 starts a chat/VoIP session setup requesttowards the user of UE 40, using the nickname, as has been chosen by theuser of UE 40 as to be used within that environment B. The communicationsession B 22 terminates in the AS chat/VoIP client 52 in the SIP-AS 50,which acts as client-SW for environment B, depicted as IP peer to peerconnection 72. The AS chat/VoIP-client 52 signals service application 54to deliver the setup request, via IMS-core network 60 and RAN 30 to theUE chat/VoIP client 41, as depicted by IP peer to peer link 70. The usergets on his UE 40 an incoming chat/VoIP-session, from“Bob128@chat/VoIP-environment-B”. When the “called party” i.e. the userof UE 40 accepts, a chat/VoIP-session is started.

When multiple communication sessions are ongoing with buddies in severalchat/VoIP communication environments 21, 22, 23, the UE chat/VoIP-client41 in cooperation with the service application 54 provides optionally amenu list at UE 40 for coordinated use of the UE's 40 I/O devices(microphone, speaker, display) for these sessions as to preventconfusion.

As a consequence of the advantageous application of a single UEchat/VoIP client 41 at the UE 40, effectively resulting in a defined RANQoS, additional advantages are provided.

Users of chat/VoIP client software, in general, are used to the conceptof a nickname, as elucidated above. When registering to a chat/VoIPcommunication environment, the chat/VoIP communication environmentassures that the chosen nickname is not yet used, i.e. unique.

To support the common notion of nicknames, the user of the “universal UEchat/VoIP-client” service in accordance with the invention also usesnicknames to address buddies in the different chat/VoIP communicationenvironments that he or she is registered to.

In an alternative, the user of UE 40 selects a specific buddy belongingto chat/VoIP communication environment 21, 22, 23 for an outgoingchat/VoIP communication session and the service application 54 willstart up the appropriate AS chat/VoIP client 51, 52, 53 as elucidatedabove.

Optionally the user of UE 40 may define more appropriate names in casebuddies have almost similar nicknames in different environments, in casea Bob128 exists in environment 22 and a Bob122 exists in environment 21,for example.

The phonebook of the user of UE 40 may comprise the buddies indicated inan alternative way. Local database 6 is arranged to store recordscomprising nicknames of buddies of any communication environment, whichcan be stored under a name, given by the user of UE 40. The UE chat/VoIPclient 41 is arranged to store at local database 6 an alternative localbuddy nickname, such as “Bob@A” for “Bob122” as buddy residing inchat/VoIP environment A 21. When local buddy name “Bob@A” is selected aschat/VoIP buddy, the UE chat/VoIP client 41 checks local database 6 forthe appropriate real nickname, and initializes a chat/VoIP communicationsession with the real nickname “Bob122” towards service application 54.

In case a nickname, e.g. “Bob120” applies to two buddies in twodifferent environments A 21 and B 22, the use of the local database 6 iseven more beneficial as the UE chat/VoIP client 41 stores records forlocal buddy names “Bob@A” and “Bob@B” in the local database 6 with anidentifier of the appropriate chat/VoIP environment A 21, and B 22. UEchat/VoIP client 41 is arranged to check for each newly entered nicknamewhether the name already exists in local database 6. In case of anexisting nickname a menu-list of available AS chat/VoIP clients 51, 52,53, corresponding to chat/VoIP environments 21, 22, 23 is provided bythe service application 54 to the UE 40 to have the user initialize aselection of the appropriate environment 21, 22, 23 for the existingreal nicknames “Bob120” and the newly entered “Bob120. On selection ofan environment for a nickname a record comprising the local nickname“Bob@A”, the real nickname “Bob120” and the identifier representing theenvironment is stored in local database 6.

When the user of UE 40 selects local nickname “Bob@A” for setting up achat/VoIP connection, UE chat/VoIP client 41 selects the record with thereal nickname and the identifier, and submits this information to theSIP-AS 50, where service application 54 supports the selection of theappropriate AS chat/VoIP client 51 to be started up according to theprovided identifier for real nickname “Bob120”.

The user of UE 40 is free to map any local nickname on real nicknames.

When the chat/VoIP communication environment 21, 22, 23 has informationthat a certain user in the environment's network is an IMS-based user(i.e. the user does not use their “regular PC-based chat/VoIP client”,but uses an IMS-based UE chat/VoIP-client 41, such as a mobiletelephone, deployed via the IMS-service “chat/VoIP-client”), thechat/VoIP communication environment 21, 22, 23 can offer additionalfunctions to this user and/or buddies.

a) Location:

When a user uses a UE 40, for example, the service application 54 in theSIP-AS 50 subscribes to an IMS-based service “Location” to publish thelocation of the UE 40 to the chat/VoIP environment 21, 22, 23 via ASchat/VoIP clients 51, 52, 53. When location information is changed, theservice application 54 receives this information from the ‘Location”service and can decide to send a status update (including the newlocation) to one or more chat/VoIP communication environments 21, 22,23. Additionally the user of UE 40 may allow the location services whenthe UE status is “idle” or “busy”.

b) Payment or Charging:

Regular users, using a “regular PC-based chat/VoIP client”, can pay forservices offered by the chat/VoIP communication environment 21, 22, 23(for example call out to the Public Switched Telephone Network). Forthis payment, an account for each communication environment 21, 22, 23must be created. Security-minded users may not want to deposit money onaccounts of one or more chat/VoIP providers. However, they most probablydon't object to paying for services in such environments using theirmobile RAN provider, in most cases being the usual trusted chat/VoIPprovider as payment broker.

IMS-based users can pay (when their IMS-provider wants to act aspayment-broker) via their telephone bill at the IMS-network provider.Alternatively SIP-AS 50 may comprise or be connected to a depositaccount 59 for chat/VoIP environments. SIP-AS 50, maintained by thetrusted network provider of RAN 30, the IMS provider or another trustedparty, is regarded as trusted. Each AS chat/VoIP client 51, 52, 53 canbe designed according to predefined rules in cooperation with serviceapplication 54 to debit deposit account 59 for use of services.

When services in a particular chat/VoIP communication environmentrequire payment, a trust relation between user and chat/VoIP provider orproviders, when using several chat/VoIP communication environments, isrequired.

c) Authentication:

A Regular UE chat/VoIP client 11, 12, 13 needs authentication in theform of an ID and password, so authentication which is based on “whatyou know”, such as providing a specific password by the user.

When the AS chat/VoIP client 51, 52, 53 has (via the service application54, and IMS-core network 60) access to IMS-Authentication services, theSubscriber Identification Module-card of the mobile telephone can beused for authentication via IP peer to peer link 70. When the IMS-basedUE chat/VoIP client 41 uses also ID and password, this authentication isbased on “what you know & what you have”, which provides bettersecurity.

As a further advantage the execution of a single UE chat/VoIP client 41instead of a multitude of chat/VoIP clients 11, 12, 13 reduces the needfor processor 3 capacity, lowers power-usage resulting in a longer useof batteries, and requires less memory.

Apart from providing a defined minimum bandwidth at the RAN 30 insteadof “best effort”, application of the invention enables:

-   -   a predefined GUI, at the I/O subunit 2 of the UE 40. The prior        art chat/VoIP UE client 11, 12, 13 deployed at the UE 1 has its        own software, its own buddy lists of IDs or nicknames, its own        identifiers, a proprietary user interface where statuses of        buddies are presented, and so on. This confusing representation        is improved by a single GUI for all supported communication        environments 21, 22, 23 and enables a consistent overview of the        functionality provided by the environments. The single UE        chat/VoIP client 41 is a universal client as the supported        communication environments 21, 22, 23 use the same GUI;    -   access to additional services offered by the mobile        telecommunications network RAN 30 for an AS chat/VoIP client 51,        52, 53, via the SIP-AS 50, resulting into telephony services        deployed in the chat/VoIP environments 21, 22, 23;    -   enabling of UE capabilities, such that OS 3 a of UE 40 allows        some level of secured functions, for example for authentication        or authorization purposes of executing applications.

Application of the invention allows an easy access for providers ofchat/VoIP environments 21, 22, 23 to have their proprietary applicationsdeployed at diverse brands and types of UE 40. Only the provider/ownerof a SIP-AS 50, in relation to a RAN 30, has to be contacted foragreeing on application of chat/VoIP environments 21, 22, 23. As aneffect of a single IMS client, each UE 40 having an IMS based UEchat/VoIP client 41 can communicate with the service application 54,thereby lessening the burden on manufacturers of having to provide asmany as chat/VoIP clients for as many as types of UE.

The present invention is not limited to the embodiments as disclosedabove, and can be modified and enhanced by those skilled in the artbeyond the scope of the present invention as disclosed in the appendedclaims without having to apply inventive skills.

What is claimed is:
 1. A method implemented by a mobile User Equipment(UE), the method comprising: executing a UE media service applicationfor representing, in a single graphical user interface (GUI) of themobile UE, status information from different media service environments;receiving, from a first server, first status information related to astatus of a first media service environment of the different mediaservice environments; receiving, from a second server, second statusinformation related to a status of a second media service environment ofthe different media service environments, wherein the first mediaservice environment and the second media service environment areoperated by different media service providers; and representing in thesingle GUI received status information, the received status informationcomprising: the first status information related to the status of thefirst media service environment, and the second status informationrelated to the status of the second media service environment.
 2. Themethod of claim 1, wherein the method further comprises registering forUE access to one of the different media service environments using theUE media service application.
 3. The method of claim 1, wherein themethod further comprises accessing, over a communication network, thedifferent media service environments.
 4. The method of claim 3, whereinthe first server and the second server are the same server, or differentservers, in the communications network; and wherein receiving the firststatus information or receiving the second status information furthercomprises interfacing with a given client on a given server in thecommunication network for accessing the different media serviceenvironments.
 5. The method of claim 1, wherein the method furthercomprises representing in the single GUI the different media serviceenvironments.
 6. The method of claim 1, wherein the method furthercomprises sending identifiers over a communications network, eachidentifier identifying an entity from which to receive any statusinformation, wherein the identifiers comprise: a first identifierrelated to the first media service environment, and a second identifierrelated to the second media service environment.
 7. The method of claim1, wherein the received status information comprises availability of auser of the first media service environment.
 8. The method of claim 1,wherein the received status information comprises availability of dataof the first media service environment.
 9. The method of claim 1,wherein the received status information comprises availability of mediafrom the first media service environment.
 10. The method of claim 1,wherein the different media service environments comprise chat or Voiceover Internet Protocol (VoIP) communication environments; and whereinthe received status information comprises data relating to a respectivechat or VoIP communication session of the first media serviceenvironment.
 11. The method of claim 1, wherein the receiving the firststatus information comprises receiving the first status informationreported in response to a status change in the first media serviceenvironment.
 12. The method of claim 1, wherein the executing the UEmedia service application comprises signaling that the UE media serviceapplication has been started by a user of the mobile UE; and wherein thereceiving the first status information comprises receiving the firststatus information responsive to the signaling.
 13. The method of claim1, wherein the executing the UE media service application comprisessignaling a change in status of the mobile UE; and wherein the receivingthe first status information comprises receiving the first statusinformation responsive to the signaling.
 14. A mobile User Equipment(UE), the mobile UE comprising communications equipment, and processingequipment, wherein said processing equipment is configured to: execute aUE media service application for representing, in a single graphicaluser interface (GUI) of the mobile UE, status information from differentmedia service environments; receive, from a first server, first statusinformation related to a status of a first media service environment ofthe different media service environments; receive, from a second server,second status information related to a status of a second media serviceenvironment of the different media service environments, wherein thefirst media service environment and the second media service environmentare operated by different media service providers; and represent in thesingle GUI received status information, the received status informationcomprising: the first status information related to the status of thefirst media service environment, and the second status informationrelated to the status of the second media service environment.
 15. Themobile UE of claim 14, wherein the processing equipment is configured toregister for UE access to one of the different media serviceenvironments using the UE media service application.
 16. The mobile UEof claim 14, wherein the processing equipment is configured to access,over a communication network, the different media service environments.17. The mobile UE of claim 16, wherein the first server and the secondserver are the same server, or different servers, in the communicationsnetwork; and wherein the processing equipment is configured to receivethe first status information or receive the second status information byinterfacing with a given client on a given server in the communicationnetwork for accessing the different media service environments.
 18. Themobile UE of claim 14, wherein the processing equipment is configured torepresent in the single GUI the different media service environments.19. The mobile UE of claim 14, wherein the processing equipment isconfigured to send identifiers over a communications network, eachidentifier identifying an entity from which to receive any statusinformation; and wherein the identifiers comprise: a first identifierrelated to the first media service environment, and a second identifierrelated to the second media service environment.
 20. The mobile UE ofclaim 14, wherein the received status information comprises availabilityof a user of the first media service environment.
 21. The mobile UE ofclaim 14, wherein the received status information comprises availabilityof data of the first media service environment.
 22. The mobile UE ofclaim 14, wherein the received status information comprises availabilityof media from the first media service environment.
 23. The mobile UE ofclaim 14, wherein the different media service environments comprise chator Voice over Internet Protocol (VoIP) communication environments; andwherein the received status information comprises data relating to arespective chat or VoIP communication session of the first media serviceenvironment.
 24. The mobile UE of claim 14, wherein the receiving thefirst status information comprises receiving the first statusinformation reported in response to a status change in the first mediaservice environment.
 25. The mobile UE of claim 14, wherein the mobileUE is configured to: execute a UE media service application by signalingthat the UE media service application has been started by a user of themobile UE; and receive the first status information responsive to thesignaling.
 26. The mobile UE of claim 14, wherein the mobile UE isconfigured to: execute a UE media service application by signaling achange in status of the mobile UE; and receive the first statusinformation responsive to the signaling.
 27. A method implemented by amobile User Equipment (UE) the method comprising: executing a UE mediaservice application for representing, in a single graphical userinterface (GUI) of the mobile UE, media service environment featuresfrom different media service environments; sending, from the UE to anapplication server, a first identifier and a second identifier that aredifferent identifiers, the different identifiers indicating differentproviders of the different media service environments; obtaining a firstmedia service environment feature mapped by the application server tothe single GUI based on the first identifier, the first media serviceenvironment feature related to a first media service environment of thedifferent media service environments; obtaining a second media serviceenvironment feature mapped by the application server to the single GUIbased on the second identifier, the second media service environmentfeature related to a second media service environment of the differentmedia service environments; and representing, in the single GUI, thefirst media service environment feature and the second media serviceenvironment feature.
 28. The method of claim 27, wherein the first mediaservice environment feature is related to an icon representation in agraphical user interface; and wherein the representing the first mediaservice environment feature comprises displaying the icon representationin the single GUI of the UE.
 29. A mobile User Equipment (UE), themobile UE comprising communications equipment, and processing equipment,wherein said processing equipment is configured to: execute a UE mediaservice application for representing, in a single graphical userinterface (GUI) of the mobile UE, media service environment featuresfrom different media service environments; send, from the UE to anapplication server, a first identifier and a second identifier that aredifferent identifiers, the different identifiers indicating differentproviders of the different media service environments; obtain a firstmedia service environment feature mapped by the application server tothe single GUI based on the first identifier, the first media serviceenvironment feature related to a first media service environment of thedifferent media service environments; obtain a second media serviceenvironment feature mapped by the application server to the single GUIbased on the second identifier, the second media service environmentfeature related to a second media service environment of the differentmedia service environments; and represent, in the single GUI, the firstmedia service environment feature and the second media serviceenvironment feature.
 30. The UE of claim 29, wherein the first mediaservice environment feature is related to an icon representation in agraphical user interface; and the processing equipment is configured torepresent the first media service environment feature by displaying theicon representation in the single GUI of the UE.